The libopenblas binaries do not include libmatgen code, so don't mark them as
exported and don't test for their presence (in linktest).
Last-Update: 2016-03-24
Gbp-Pq: Name matgen-symbols-not-included.patch
* It is done so that duplicate code with libopenblas.so.0 is kept as low as
possible. Only the symbols from the external BLAS/LAPACK API are incorporated
in the shared libraries. The rest is obtained by dynamic linking against
libopenblas.so.0. This also gives access to some extra OpenBLAS symbols, in
order to differentiate it at runtime from other BLAS implementations (see
#960728).
The -rpath,'$ORIGIN' is there to ensure that the OpenBLAS flavour used is
the one selected in the lib{blas,lapack}.so.3 alternative, and not the one
selected in the libopenblas.so.0 alternative.
* See also override_dh_shlibdeps in debian/rules
* Also order the files when calling `ar' or $(CC), to make
the build reproducible (see #824639)
* Also link the shared blas and lapack against gomp (see #945791)
Last-Update: 2020-07-31
Gbp-Pq: Name shared-blas-lapack.patch
Adapt build system for the absence of lapack-netlib/ and relapack directories.
Forwarded: not-needed
Last-Update: 2017-07-27
Instead use the binary provided by package liblapack-pic, stripping from it the
symbols that are overridden by OpenBLAS.
Last-Update: 2017-07-27
Gbp-Pq: Name no-embedded-lapack.patch
Use flags suitable for armhf port when TARGET=ARMV6
Forwarded: not-needed
Last-Update: 2015-04-29
See debian/rules for an explanation of why we can't use TARGET=ARMV7 on armhf.
Also, if we don't explicitly set the -march and -mfpu flags, the resulting
static libraries crash with SIGILL (reason not yet elucidated).
Last-Update: 2015-04-29
Gbp-Pq: Name arm-gcc-flags.patch
The libopenblas binaries do not include libmatgen code, so don't mark them as
exported and don't test for their presence (in linktest).
Last-Update: 2016-03-24
Gbp-Pq: Name matgen-symbols-not-included.patch
* It is done so that duplicate code with libopenblas.so.0 is kept as low as
possible. Only the symbols from the external BLAS/LAPACK API are incorporated
in the shared libraries. The rest is obtained by dynamic linking against
libopenblas.so.0. This also gives access to some extra OpenBLAS symbols, in
order to differentiate it at runtime from other BLAS implementations (see
#960728).
The -rpath,'$ORIGIN' is there to ensure that the OpenBLAS flavour used is
the one selected in the lib{blas,lapack}.so.3 alternative, and not the one
selected in the libopenblas.so.0 alternative.
* See also override_dh_shlibdeps in debian/rules
* Also order the files when calling `ar' or $(CC), to make
the build reproducible (see #824639)
* Also link the shared blas and lapack against gomp (see #945791)
Last-Update: 2020-07-31
Gbp-Pq: Name shared-blas-lapack.patch
Adapt build system for the absence of lapack-netlib/ and relapack directories.
Forwarded: not-needed
Last-Update: 2017-07-27
Instead use the binary provided by package liblapack-pic, stripping from it the
symbols that are overridden by OpenBLAS.
Last-Update: 2017-07-27
Gbp-Pq: Name no-embedded-lapack.patch
Use flags suitable for armhf port when TARGET=ARMV6
Forwarded: not-needed
Last-Update: 2015-04-29
See debian/rules for an explanation of why we can't use TARGET=ARMV7 on armhf.
Also, if we don't explicitly set the -march and -mfpu flags, the resulting
static libraries crash with SIGILL (reason not yet elucidated).
Last-Update: 2015-04-29
Gbp-Pq: Name arm-gcc-flags.patch
The libopenblas binaries do not include libmatgen code, so don't mark them as
exported and don't test for their presence (in linktest).
Last-Update: 2016-03-24
Gbp-Pq: Name matgen-symbols-not-included.patch
* It is done so that duplicate code with libopenblas.so.0 is kept as low as
possible. Only the symbols from the external BLAS/LAPACK API are incorporated
in the shared libraries. The rest is obtained by dynamic linking against
libopenblas.so.0. This also gives access to some extra OpenBLAS symbols, in
order to differentiate it at runtime from other BLAS implementations (see
#960728).
The -rpath,'$ORIGIN' is there to ensure that the OpenBLAS flavour used is
the one selected in the lib{blas,lapack}.so.3 alternative, and not the one
selected in the libopenblas.so.0 alternative.
* See also override_dh_shlibdeps in debian/rules
* Also order the files when calling `ar' or $(CC), to make
the build reproducible (see #824639)
* Also link the shared blas and lapack against gomp (see #945791)
Last-Update: 2020-07-31
Gbp-Pq: Name shared-blas-lapack.patch
Adapt build system for the absence of lapack-netlib/ and relapack directories.
Forwarded: not-needed
Last-Update: 2017-07-27
Instead use the binary provided by package liblapack-pic, stripping from it the
symbols that are overridden by OpenBLAS.
Last-Update: 2017-07-27
Gbp-Pq: Name no-embedded-lapack.patch
Use flags suitable for armhf port when TARGET=ARMV6
Forwarded: not-needed
Last-Update: 2015-04-29
See debian/rules for an explanation of why we can't use TARGET=ARMV7 on armhf.
Also, if we don't explicitly set the -march and -mfpu flags, the resulting
static libraries crash with SIGILL (reason not yet elucidated).
Last-Update: 2015-04-29
Gbp-Pq: Name arm-gcc-flags.patch
The libopenblas binaries do not include libmatgen code, so don't mark them as
exported and don't test for their presence (in linktest).
Last-Update: 2016-03-24
Gbp-Pq: Name matgen-symbols-not-included.patch
* It is done so that duplicate code with libopenblas.so.0 is kept as low as
possible. Only the symbols from the external BLAS/LAPACK API are incorporated
in the shared libraries. The rest is obtained by dynamic linking against
libopenblas.so.0. This also gives access to some extra OpenBLAS symbols, in
order to differentiate it at runtime from other BLAS implementations (see
#960728).
The -rpath,'$ORIGIN' is there to ensure that the OpenBLAS flavour used is
the one selected in the lib{blas,lapack}.so.3 alternative, and not the one
selected in the libopenblas.so.0 alternative.
* See also override_dh_shlibdeps in debian/rules
* Also order the files when calling `ar' or $(CC), to make
the build reproducible (see #824639)
* Also link the shared blas and lapack against gomp (see #945791)
Last-Update: 2020-07-31
Gbp-Pq: Name shared-blas-lapack.patch
Adapt build system for the absence of lapack-netlib/ and relapack directories.
Forwarded: not-needed
Last-Update: 2017-07-27
Instead use the binary provided by package liblapack-pic, stripping from it the
symbols that are overridden by OpenBLAS.
Last-Update: 2017-07-27
Gbp-Pq: Name no-embedded-lapack.patch
Use flags suitable for armhf port when TARGET=ARMV6
Forwarded: not-needed
Last-Update: 2015-04-29
See debian/rules for an explanation of why we can't use TARGET=ARMV7 on armhf.
Also, if we don't explicitly set the -march and -mfpu flags, the resulting
static libraries crash with SIGILL (reason not yet elucidated).
Last-Update: 2015-04-29
Gbp-Pq: Name arm-gcc-flags.patch
The libopenblas binaries do not include libmatgen code, so don't mark them as
exported and don't test for their presence (in linktest).
Last-Update: 2016-03-24
Gbp-Pq: Name matgen-symbols-not-included.patch
* It is done so that duplicate code with libopenblas.so.0 is kept as low as
possible. Only the symbols from the external BLAS/LAPACK API are incorporated
in the shared libraries. The rest is obtained by dynamic linking against
libopenblas.so.0. This also gives access to some extra OpenBLAS symbols, in
order to differentiate it at runtime from other BLAS implementations (see
#960728).
The -rpath,'$ORIGIN' is there to ensure that the OpenBLAS flavour used is
the one selected in the lib{blas,lapack}.so.3 alternative, and not the one
selected in the libopenblas.so.0 alternative.
* See also override_dh_shlibdeps in debian/rules
* Also order the files when calling `ar' or $(CC), to make
the build reproducible (see #824639)
* Also link the shared blas and lapack against gomp (see #945791)
Last-Update: 2020-07-31
Gbp-Pq: Name shared-blas-lapack.patch
Adapt build system for the absence of lapack-netlib/ and relapack directories.
Forwarded: not-needed
Last-Update: 2017-07-27
Instead use the binary provided by package liblapack-pic, stripping from it the
symbols that are overridden by OpenBLAS.
Last-Update: 2017-07-27
Gbp-Pq: Name no-embedded-lapack.patch
Use flags suitable for armhf port when TARGET=ARMV6
Forwarded: not-needed
Last-Update: 2015-04-29
See debian/rules for an explanation of why we can't use TARGET=ARMV7 on armhf.
Also, if we don't explicitly set the -march and -mfpu flags, the resulting
static libraries crash with SIGILL (reason not yet elucidated).
Last-Update: 2015-04-29
Gbp-Pq: Name arm-gcc-flags.patch
The libopenblas binaries do not include libmatgen code, so don't mark them as
exported and don't test for their presence (in linktest).
Last-Update: 2016-03-24
Gbp-Pq: Name matgen-symbols-not-included.patch
* It is done so that duplicate code with libopenblas.so.0 is kept as low as
possible. Only the symbols from the external BLAS/LAPACK API are incorporated
in the shared libraries. The rest is obtained by dynamic linking against
libopenblas.so.0. This also gives access to some extra OpenBLAS symbols, in
order to differentiate it at runtime from other BLAS implementations (see
#960728).
The -rpath,'$ORIGIN' is there to ensure that the OpenBLAS flavour used is
the one selected in the lib{blas,lapack}.so.3 alternative, and not the one
selected in the libopenblas.so.0 alternative.
* See also override_dh_shlibdeps in debian/rules
* Also order the files when calling `ar' or $(CC), to make
the build reproducible (see #824639)
* Also link the shared blas and lapack against gomp (see #945791)
Last-Update: 2020-07-31
Gbp-Pq: Name shared-blas-lapack.patch
Adapt build system for the absence of lapack-netlib/ and relapack directories.
Forwarded: not-needed
Last-Update: 2017-07-27
Instead use the binary provided by package liblapack-pic, stripping from it the
symbols that are overridden by OpenBLAS.
Last-Update: 2017-07-27
Gbp-Pq: Name no-embedded-lapack.patch
Use flags suitable for armhf port when TARGET=ARMV6
Forwarded: not-needed
Last-Update: 2015-04-29
See debian/rules for an explanation of why we can't use TARGET=ARMV7 on armhf.
Also, if we don't explicitly set the -march and -mfpu flags, the resulting
static libraries crash with SIGILL (reason not yet elucidated).
Last-Update: 2015-04-29
Gbp-Pq: Name arm-gcc-flags.patch
Those functions are not yet in LAPACK 3.11 (they are scheduled for a future
LAPACK release). Since the Debian package for OpenBLAS relies on the latest
stable LAPACK release, we have to (temporarily) remove support for them.
The libopenblas binaries do not include libmatgen code, so don't mark them as
exported and don't test for their presence (in linktest).
Last-Update: 2016-03-24
Gbp-Pq: Name matgen-symbols-not-included.patch
* It is done so that duplicate code with libopenblas.so.0 is kept as low as
possible. Only the symbols from the external BLAS/LAPACK API are incorporated
in the shared libraries. The rest is obtained by dynamic linking against
libopenblas.so.0. This also gives access to some extra OpenBLAS symbols, in
order to differentiate it at runtime from other BLAS implementations (see
#960728).
The -rpath,'$ORIGIN' is there to ensure that the OpenBLAS flavour used is
the one selected in the lib{blas,lapack}.so.3 alternative, and not the one
selected in the libopenblas.so.0 alternative.
* See also override_dh_shlibdeps in debian/rules
* Also order the files when calling `ar' or $(CC), to make
the build reproducible (see #824639)
* Also link the shared blas and lapack against gomp (see #945791)
Last-Update: 2020-07-31
Gbp-Pq: Name shared-blas-lapack.patch
Adapt build system for the absence of lapack-netlib/ and relapack directories.
Forwarded: not-needed
Last-Update: 2017-07-27
Instead use the binary provided by package liblapack-pic, stripping from it the
symbols that are overridden by OpenBLAS.
Last-Update: 2017-07-27
Gbp-Pq: Name no-embedded-lapack.patch
Use flags suitable for armhf port when TARGET=ARMV6
Forwarded: not-needed
Last-Update: 2015-04-29
See debian/rules for an explanation of why we can't use TARGET=ARMV7 on armhf.
Also, if we don't explicitly set the -march and -mfpu flags, the resulting
static libraries crash with SIGILL (reason not yet elucidated).
Last-Update: 2015-04-29
Gbp-Pq: Name arm-gcc-flags.patch
Those functions are not yet in LAPACK 3.11 (they are scheduled for a future
LAPACK release). Since the Debian package for OpenBLAS relies on the latest
stable LAPACK release, we have to (temporarily) remove support for them.
The libopenblas binaries do not include libmatgen code, so don't mark them as
exported and don't test for their presence (in linktest).
Last-Update: 2016-03-24
Gbp-Pq: Name matgen-symbols-not-included.patch
* It is done so that duplicate code with libopenblas.so.0 is kept as low as
possible. Only the symbols from the external BLAS/LAPACK API are incorporated
in the shared libraries. The rest is obtained by dynamic linking against
libopenblas.so.0. This also gives access to some extra OpenBLAS symbols, in
order to differentiate it at runtime from other BLAS implementations (see
#960728).
The -rpath,'$ORIGIN' is there to ensure that the OpenBLAS flavour used is
the one selected in the lib{blas,lapack}.so.3 alternative, and not the one
selected in the libopenblas.so.0 alternative.
* See also override_dh_shlibdeps in debian/rules
* Also order the files when calling `ar' or $(CC), to make
the build reproducible (see #824639)
* Also link the shared blas and lapack against gomp (see #945791)
Last-Update: 2020-07-31
Gbp-Pq: Name shared-blas-lapack.patch
Adapt build system for the absence of lapack-netlib/ and relapack directories.
Forwarded: not-needed
Last-Update: 2017-07-27
Instead use the binary provided by package liblapack-pic, stripping from it the
symbols that are overridden by OpenBLAS.
Last-Update: 2017-07-27
Gbp-Pq: Name no-embedded-lapack.patch
[changes brought forward from 0.2.15-1+rpi1 by Peter Michael Green <plugwash@raspbian.org> at Fri, 11 Mar 2016 23:39:32 +0000]
* Disable arm-gcc-flags.patch which was enforcing gcc flags that are wrong
for raspbian.
Those functions are not yet in LAPACK 3.11 (they are scheduled for a future
LAPACK release). Since the Debian package for OpenBLAS relies on the latest
stable LAPACK release, we have to (temporarily) remove support for them.
The libopenblas binaries do not include libmatgen code, so don't mark them as
exported and don't test for their presence (in linktest).
Last-Update: 2016-03-24
Gbp-Pq: Name matgen-symbols-not-included.patch
* It is done so that duplicate code with libopenblas.so.0 is kept as low as
possible. Only the symbols from the external BLAS/LAPACK API are incorporated
in the shared libraries. The rest is obtained by dynamic linking against
libopenblas.so.0. This also gives access to some extra OpenBLAS symbols, in
order to differentiate it at runtime from other BLAS implementations (see
#960728).
The -rpath,'$ORIGIN' is there to ensure that the OpenBLAS flavour used is
the one selected in the lib{blas,lapack}.so.3 alternative, and not the one
selected in the libopenblas.so.0 alternative.
* See also override_dh_shlibdeps in debian/rules
* Also order the files when calling `ar' or $(CC), to make
the build reproducible (see #824639)
* Also link the shared blas and lapack against gomp (see #945791)
Last-Update: 2020-07-31
Gbp-Pq: Name shared-blas-lapack.patch
Adapt build system for the absence of lapack-netlib/ and relapack directories.
Forwarded: not-needed
Last-Update: 2017-07-27
Instead use the binary provided by package liblapack-pic, stripping from it the
symbols that are overridden by OpenBLAS.
Last-Update: 2017-07-27
Gbp-Pq: Name no-embedded-lapack.patch
projects / openblas.git / log